Skip to content

chore(nextjs): Support unstable_rethrow inside clerkMiddleware - #4347

Merged
jacekradko merged 10 commits into
feat/nextjs-15-compatfrom
elef/sdki-708-support-unstable_rethrow-inside-clerkmiddleware
Oct 22, 2024
Merged

chore(nextjs): Support unstable_rethrow inside clerkMiddleware#4347
jacekradko merged 10 commits into
feat/nextjs-15-compatfrom
elef/sdki-708-support-unstable_rethrow-inside-clerkmiddleware

Conversation

@panteliselef

@panteliselef panteliselef commented Oct 17, 2024

Copy link
Copy Markdown
Contributor

Description

We changed the errors thrown by protect() inside clerkMiddleware in order for unstable_rethrow to recognise them and rethrow them.

Checklist

  • npm test runs as expected.
  • npm run build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

@changeset-bot

changeset-bot Bot commented Oct 17, 2024

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4ed45dd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@clerk/nextjs Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@panteliselef panteliselef self-assigned this Oct 18, 2024
Comment thread packages/nextjs/src/server/nextErrors.ts
@jacekradko
jacekradko changed the base branch from main to feat/nextjs-15-compat October 21, 2024 23:49
@jacekradko
jacekradko merged commit 7149cc2 into feat/nextjs-15-compat Oct 22, 2024
@jacekradko
jacekradko deleted the elef/sdki-708-support-unstable_rethrow-inside-clerkmiddleware branch October 22, 2024 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants